home *** CD-ROM | disk | FTP | other *** search
- Path: news.cc.uic.edu!sunphy1!olczyk
- From: olczyk@sunphy1 (Thadeus Olczyk)
- Newsgroups: comp.lang.c++
- Subject: Re: Idle curiosity: Delphi properties in C++
- Date: 12 Jan 1996 23:37:32 GMT
- Organization: University of Illinois at Chicago
- Message-ID: <4d6rbs$5uj2@tigger.cc.uic.edu>
- References: <4cm1hp$mok$1@canberra.DIALix.oz.au> <L0u7wg2yqzFJ083yn@iaccess.za>
- NNTP-Posting-Host: sunphy1.phy.uic.edu
- X-Newsreader: TIN [version 1.2 PL2]
-
- Vince Risi (vincer@iaccess.za) wrote:
- : > One major advantage Delphi has over Borland Pascal 7.0, Visual Basic and
- : > (apparently) C++ is called a property.
-
- : You cannot seriously believe that the C++ community will even concede
- : that properties are COOL. Next thing you will be trying to convince
- Properties are properties. Their purpose is to set values of components.
- VBX's and OCX's have their own version of properties and therefore so do languages which generate VBX's and OCX's.
-
- : them that units are COOL. BS may even have to concede that the greatly
- Units are simply compilation units. Any language that is meant to be used
- for programs more then a thousand lines must have some version of units,
- in C++ it is header/source file combinations.
-
- The dificulty in Delphi is that the interface and implementation parts
- must be held in the same file. When files get large it makes them unweildly.
- ---------------------------
- Thaddeus L. Olczyk
-
-